User equipments, base stations and methods for transport block determination for mini-slot pusch

ABSTRACT

A user equipment (UE) is described. The UE includes receiving circuitry configured to receive resource allocation information of a physical uplink shared channel (PUSCH) and a number of repetitions for the PUSCH. The UE also includes control circuitry configured to calculate a transport block size (TBS) for the PUSCH. The UE further includes transmission circuitry configured to transmit the PUSCH. The TBS is calculated based on a number of resource elements (REs) for a demodulation reference signal (DMRS), REs for additional DMRS, and REs for a DMRS added right after a slot boundary for a repetition of the PUSCH.

CROSS REFERENCE

This Nonprovisional application claims priority under 35 U.S.C. § 119 onprovisional Application No. 62,841,971 on May 2, 2019, the entirecontents of which are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates generally to communication systems. Morespecifically, the present disclosure relates to new signaling,procedures, user equipment (UE) and base stations for configuration foruser equipments, base stations and methods for transport blockdetermination for mini-slot physical uplink shared channel (PUSCH).

BACKGROUND ART

Wireless communication devices have become smaller and more powerful inorder to meet consumer needs and to improve portability and convenience.Consumers have become dependent upon wireless communication devices andhave come to expect reliable service, expanded areas of coverage andincreased functionality. A wireless communication system may providecommunication for a number of wireless communication devices, each ofwhich may be serviced by a base station. A base station may be a devicethat communicates with wireless communication devices.

As wireless communication devices have advanced, improvements incommunication capacity, speed, flexibility and/or efficiency have beensought. However, improving communication capacity, speed, flexibilityand/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

SUMMARY OF INVENTION

In one example, a user equipment comprising: receiving circuitryconfigured to receive resource allocation information of a physicaluplink shared channel (PUSCH) and a number of repetitions for the PUSCH;control circuitry configured to calculate a transport block size (TBS)for the PUSCH; and transmission circuitry configured to transmit thePUSCH, wherein the TBS is calculated based on a number of resourceelements (REs) for a demodulation reference signal (DMRS), REs foradditional DMRS, and REs for a DMRS added right after a slot boundaryfor a repetition of the PUSCH.

In one example, a base station apparatus comprising: transmissioncircuitry configured to transmit resource allocation information of aphysical uplink shared channel (PUSCH) and a number of repetitions forthe PUSCH; and receiving circuitry configured to receive the PUSCH,wherein a transport block size (TBS) for the PUSCH is calculated basedon a number of resource elements (REs) for a demodulation referencesignal (DMRS), REs for additional DMRS, and REs for a DMRS added rightafter a slot boundary for a repetition of the PUSCH.

In one example, a communication method of a user equipment comprising:receiving resource allocation information of a physical uplink sharedchannel (PUSCH) and a number of repetitions for the PUSCH; calculating atransport block size (TBS) for the PUSCH; and transmitting the PUSCH,wherein the TBS is calculated based on a number of resource elements(REs) for a demodulation reference signal (DMRS), REs for additionalDMRS, and REs for a DMRS added right after a slot boundary for arepetition of the PUSCH.

In one example, a communication method of a base station apparatuscomprising: transmitting resource allocation information of a physicaluplink shared channel (PUSCH) and a number of repetitions for the PUSCH;and receiving the PUSCH, wherein a transport block size (TBS) for thePUSCH is calculated based on a number of resource elements (REs) for ademodulation reference signal (DMRS), REs for additional DMRS, and REsfor a DMRS added right after a slot boundary for a repetition of thePUSCH.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating one implementation of one or morebase station apparatuses (gNBs) and one or more user equipments (UEs) inwhich systems and methods for signaling may be implemented.

FIG. 2 shows examples of multiple numerologies.

FIG. 3 is a diagram illustrating one example of a resource grid andresource block.

FIG. 4 shows examples of resource regions.

FIG. 5 shows an example of the mini-slot repetition and multi-segmenttransmissions.

FIG. 6 illustrates an example of multi-segment transmission.

FIG. 7 illustrates another example of mini-slot repetition transmission.

FIG. 8 illustrates various components that may be utilized in a UE.

FIG. 9 illustrates various components that may be utilized in a gNB.

FIG. 10 is a block diagram illustrating one implementation of a UE inwhich one or more of the systems and/or methods described herein may beimplemented.

FIG. 11 is a block diagram illustrating one implementation of a gNB inwhich one or more of the systems and/or methods described herein may beimplemented.

FIG. 12 is a block diagram illustrating one implementation of a gNB.

FIG. 13 is a block diagram illustrating one implementation of a UE.

FIG. 14 is a flow diagram illustrating a communication method by a UE.

FIG. 15 is a flow diagram illustrating a communication method by a gNB.

FIG. 16 illustrates an example of the mini-slot repetition and/ormulti-segment transmission.

DESCRIPTION OF EMBODIMENTS

A user equipment (UE) is described. The UE includes receiving circuitryconfigured to receive resource allocation information of a physicaluplink shared channel (PUSCH) and a number of repetitions for the PUSCH.The UE also includes control circuitry configured to calculate atransport block size (TBS) for the PUSCH. The UE further includestransmission circuitry configured to transmit the PUSCH. The TBS iscalculated based on a number of resource elements (REs) for ademodulation reference signal (DMRS), REs for additional DMRS, and REsfor a DMRS added right after a slot boundary for a repetition of thePUSCH.

A base station apparatus is also described. The base station apparatusincludes transmission circuitry configured to transmit resourceallocation information of a PUSCH and a number of repetitions for thePUSCH. The base station apparatus also includes receiving circuitryconfigured to receive the PUSCH. A TBS for the PUSCH is calculated basedon a number of REs for a DMRS, REs for additional DMRS, and REs for aDMRS added right after a slot boundary for a repetition of the PUSCH.

A communication method of a user equipment is also described. The methodincludes receiving resource allocation information of a PUSCH and anumber of repetitions for the PUSCH. The method also includescalculating a TBS for the PUSCH. The method further includestransmitting the PUSCH. The TBS is calculated based on a number of REsfor a DMRS, REs for additional DMRS, and REs for a DMRS added rightafter a slot boundary for a repetition of the PUSCH.

A communication method of a base station apparatus is also described.The method includes transmitting resource allocation information of aPUSCH and a number of repetitions for the PUSCH. The method alsoincludes receiving the PUSCH. A TBS for the PUSCH is calculated based ona number of REs for a DMRS, REs for additional DMRS, and REs for a DMRSadded right after a slot boundary for a repetition of the PUSCH.

The 3rd Generation Partnership Project, also referred to as “3GPP,” is acollaboration agreement that aims to define globally applicabletechnical specifications and technical reports for third and fourthgeneration wireless communication systems. The 3GPP may definespecifications for next generation mobile networks, systems and devices.

3GPP Long Term Evolution (LTE) is the name given to a project to improvethe Universal Mobile Telecommunications System (UMTS) mobile phone ordevice standard to cope with future requirements. In one aspect, UMTShas been modified to provide support and specification for the EvolvedUniversal Terrestrial Radio Access (E-UTRA) and Evolved UniversalTerrestrial Radio Access Network (E-UTRAN).

At least some aspects of the systems and methods disclosed herein may bedescribed in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and otherstandards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14 and/or 15).However, the scope of the present disclosure should not be limited inthis regard. At least some aspects of the systems and methods disclosedherein may be utilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used tocommunicate voice and/or data to a base station, which in turn maycommunicate with a network of devices (e.g., public switched telephonenetwork (PSTN), the Internet, etc.). In describing systems and methodsherein, a wireless communication device may alternatively be referred toas a mobile station, a UE, an access terminal, a subscriber station, amobile terminal, a remote station, a user terminal, a terminal, asubscriber unit, a mobile device, etc. Examples of wirelesscommunication devices include cellular phones, smart phones, personaldigital assistants (PDAs), laptop computers, netbooks, e-readers,wireless modems, etc. In 3GPP specifications, a wireless communicationdevice is typically referred to as a UE. However, as the scope of thepresent disclosure should not be limited to the 3GPP standards, theterms “UE” and “wireless communication device” may be usedinterchangeably herein to mean the more general term “wirelesscommunication device.” A UE may also be more generally referred to as aterminal device.

In 3GPP specifications, a base station is typically referred to as aNode B, an evolved Node B (eNB), a home enhanced or evolved Node B(HeNB) or some other similar terminology. As the scope of the disclosureshould not be limited to 3GPP standards, the terms “base station,” “NodeB,” “eNB,” “gNB” and “HeNB” may be used interchangeably herein to meanthe more general term “base station.” Furthermore, the term “basestation” may be used to denote an access point. An access point may bean electronic device that provides access to a network (e.g., Local AreaNetwork (LAN), the Internet, etc.) for wireless communication devices.The term “communication device” may be used to denote both a wirelesscommunication device and/or a base station. An eNB may also be moregenerally referred to as a base station device.

It should be noted that as used herein, a “cell” may be anycommunication channel that is specified by standardization or regulatorybodies to be used for International Mobile Telecommunications-Advanced(IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP aslicensed bands (e.g., frequency bands) to be used for communicationbetween an eNB and a UE. It should also be noted that in E-UTRA andEUTRAN overall description, as used herein, a “cell” may be defined as“combination of downlink and optionally uplink resources.” The linkingbetween the carrier frequency of the downlink resources and the carrierfrequency of the uplink resources may be indicated in the systeminformation transmitted on the downlink resources.

The 5th generation communication systems, dubbed NR (New Radiotechnologies) by 3GPP, envision the use of time/frequency/spaceresources to allow for services, such as eMBB (enhanced MobileBroad-Band) transmission, URLLC (Ultra Reliable and Low LatencyCommunication) transmission, and eMTC (massive Machine TypeCommunication) transmission. And, in NR, transmissions for differentservices may be specified (e.g., configured) for one or more bandwidthparts (BWPs) in a serving cell and/or for one or more serving cells. Auser equipment (UE) may receive a downlink signal(s) and/or transmit anuplink signal(s) in the BWP(s) of the serving cell and/or the servingcell(s).

In order for the services to use the time, frequency, and/or spaceresources efficiently, it would be useful to be able to efficientlycontrol downlink and/or uplink transmissions. Therefore, a procedure forefficient control of downlink and/or uplink transmissions should bedesigned. Accordingly, a detailed design of a procedure for downlinkand/or uplink transmissions may be beneficial.

UCI for URLLC needs higher reliability and lower latency than eMBB. Inone aspect, the described systems and methods can achieve the lowerlatency in mini-slot repetition by using the earliest DMRS satisfyingthe timing equal to or greater than the indicated timing in repeatedPUSCH. In another aspect, the described systems and methods, can achievethe higher reliability by using multiple parameters for UCI multiplexingon PUSCH.

Various examples of the systems and methods disclosed herein are nowdescribed with reference to the Figures, where like reference numbersmay indicate functionally similar elements. The systems and methods asgenerally described and illustrated in the Figures herein could bearranged and designed in a wide variety of different implementations.Thus, the following more detailed description of severalimplementations, as represented in the Figures, is not intended to limitscope, as claimed, but is merely representative of the systems andmethods.

FIG. 1 is a block diagram illustrating one implementation of one or moregNBs 160 and one or more UEs 102 in which systems and methods forsignaling may be implemented. The one or more UEs 102 communicate withone or more gNBs 160 using one or more physical antennas 122 a-n. Forexample, a UE 102 transmits electromagnetic signals to the gNB 160 andreceives electromagnetic signals from the gNB 160 using the one or morephysical antennas 122 a-n. The gNB 160 communicates with the UE 102using one or more physical antennas 180 a-n. In some implementations,the term “base station,” “eNB,” and/or “gNB” may refer to and/or may bereplaced by the term “Transmission Reception Point (TRP).” For example,the gNB 160 described in connection with FIG. 1 may be a TRP in someimplementations.

The UE 102 and the gNB 160 may use one or more channels and/or one ormore signals 119, 121 to communicate with each other. For example, theUE 102 may transmit information or data to the gNB 160 using one or moreuplink channels 121. Examples of uplink channels 121 include a physicalshared channel (e.g., PUSCH (physical uplink shared channel)) and/or aphysical control channel (e.g., PUCCH (physical uplink controlchannel)), etc. The one or more gNBs 160 may also transmit informationor data to the one or more UEs 102 using one or more downlink channels119, for instance. Examples of downlink channels 119 include a physicalshared channel (e.g., PDCCH (physical downlink shared channel) and/or aphysical control channel (PDCCH (physical downlink control channel)),etc. Other kinds of channels and/or signals may be used.

Each of the one or more UEs 102 may include one or more transceivers118, one or more demodulators 114, one or more decoders 108, one or moreencoders 150, one or more modulators 154, a data buffer 104 and a UEoperations module 124. For example, one or more reception and/ortransmission paths may be implemented in the UE 102. For convenience,only a single transceiver 118, decoder 108, demodulator 114, encoder 150and modulator 154 are illustrated in the UE 102, though multipleparallel elements (e.g., transceivers 118, decoders 108, demodulators114, encoders 150 and modulators 154) may be implemented.

The transceiver 118 may include one or more receivers 120 and one ormore transmitters 158. The one or more receivers 120 may receive signalsfrom the gNB 160 using one or more antennas 122 a-n. For example, thereceiver 120 may receive and downconvert signals to produce one or morereceived signals 116. The one or more received signals 116 may beprovided to a demodulator 114. The one or more transmitters 158 maytransmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert andtransmit one or more modulated signals 156.

The demodulator 114 may demodulate the one or more received signals 116to produce one or more demodulated signals 112. The one or moredemodulated signals 112 may be provided to the decoder 108. The UE 102may use the decoder 108 to decode signals. The decoder 108 may producedecoded signals 110, which may include a UE-decoded signal 106 (alsoreferred to as a first UE-decoded signal 106). For example, the firstUE-decoded signal 106 may comprise received payload data, which may bestored in a data buffer 104. Another signal included in the decodedsignals 110 (also referred to as a second UE-decoded signal 110) maycomprise overhead data and/or control data. For example, the second UEdecoded signal 110 may provide data that may be used by the UEoperations module 124 to perform one or more operations.

In general, the UE operations module 124 may enable the UE 102 tocommunicate with the one or more gNBs 160. The UE operations module 124may include one or more of a UE scheduling module 126.

The UE scheduling module 126 may perform downlink reception(s) anduplink transmission(s). The downlink reception(s) include reception ofdata, reception of downlink control information, and/or reception ofdownlink reference signals. Also, the uplink transmissions includetransmission of data, transmission of uplink control information, and/ortransmission of uplink reference signals.

In a radio communication system, physical channels (uplink physicalchannels and/or downlink physical channels) may be defined. The physicalchannels (uplink physical channels and/or downlink physical channels)may be used for transmitting information that is delivered from a higherlayer.

For example, in uplink, a PRACH (Physical Random Access Channel) may bedefined. In some approaches, the PRACH (e.g., the random accessprocedure) may be used for an initial access connection establishmentprocedure, a handover procedure, a connection re-establishment, a timingadjustment (e.g., a synchronization for an uplink transmission, for ULsynchronization) and/or for requesting an uplink shared channel (UL-SCH)resource (e.g., the uplink physical shared channel (PSCH) (e.g., PUCCH)resource).

In another example, a physical uplink control channel (PUCCH) may bedefined. The PUCCH may be used for transmitting uplink controlinformation (UCI). The UCI may include hybrid automatic repeatrequest-acknowledgement (HARQ-ACK), channel state information (CSI)and/or a scheduling request (SR). The HARQ-ACK is used for indicating apositive acknowledgement (ACK) or a negative acknowledgment (NACK) fordownlink data (e.g., Transport block(s), Medium Access Control ProtocolData Unit (MAC PDU) and/or Downlink Shared Channel (DL-SCH)). The CSI isused for indicating state of downlink channel (e.g., a downlinksignal(s)). Also, the SR is used for requesting resources of uplink data(e.g., Transport block(s), MAC PDU and/or Uplink Shared Channel(UL-SCH)).

Here, the DL-SCH and/or the UL-SCH may be a transport channel that isused in the MAC layer. Also, a transport block(s) (TB(s)) and/or a MACPDU may be defined as a unit(s) of the transport channel used in the MAClayer. The transport block may be defined as a unit of data deliveredfrom the MAC layer to the physical layer. The MAC layer may deliver thetransport block to the physical layer (e.g., the MAC layer delivers thedata as the transport block to the physical layer). In the physicallayer, the transport block may be mapped to one or more codewords.

In downlink, a physical downlink control channel (PDCCH) may be defined.The PDCCH may be used for transmitting downlink control information(DCI). Here, more than one DCI formats may be defined for DCItransmission on the PDCCH. Namely, fields may be defined in the DCIformat(s), and the fields are mapped to the information bits (e.g., DCIbits).

For example, a DCI format 1_0 that is used for scheduling of the PDSCHin the cell may be defined as the DCI format for the downlink. Also, asdescribed herein one or more Radio Network Temporary Identifiers (e.g.,the Cell RNTI(s) (C-RNTI(s)), the Configured Scheduling RNTI(s)(CS-RNTI(s)), the System Information RNTI(s) (SI-RNTI(s)), the RandomAccess RNTI(s) (RA-RNTI(s)), and/or a first RNTI may be used to transmitthe DCI format 1_0. Also, the DCI format 1_0 may be monitored (e.g.,transmitted, mapped) in the Common Search Space (CSS) and/or the UESpecific Search space (USS). Alternatively, the DCI format 1_0 may bemonitored (e.g., transmitted, mapped) in the CSS only.

For example, the DCI included in the DCI format 1_0 may be a frequencydomain resource assignment (e.g., for the PDSCH). Additionally oralternatively, the DCI included in the DCI format 1_0 may be a timedomain resource assignment (e.g., for the PDSCH). Additionally oralternatively, the DCI included in the DCI format 1_0 may be amodulation and coding scheme (e.g., for the PDSCH). Additionally oralternatively, or alternatively, the DCI included in the DCI format 1_0may be a new data indicator. Additionally or alternatively, the DCIincluded in the DCI format 1_0 may be a TPC (e.g., Transmission PowerControl) command for scheduled PUCCH. Additionally or alternatively, theDCI included in the DCI format 1_0 may be a PUCCH resource indicator.Additionally or alternatively, the DCI included in the DCI format 1_0may be a PDSCH-to-HARQ feedback timing indicator. Additionally oralternatively, the DCI included in the DCI format 1_0 may be a priorityindication (e.g., for the PDSCH transmission and/or the PDSCHreception). Additionally or alternatively, the DCI included in the DCIformat 1_0 may be the priority indication (e.g., for the HARQ-ACKtransmission for the PDSCH and/or the HARQ-ACK reception for the PDSCH).

Here, the priority indication may be used for indicating a priority(e.g., 2-bit information, 00: the lowest priority, 01: the lowerpriority, 10: the higher priority, and/or 11: the highest priority) forthe PDSCH transmission and/or the PDSCH reception. For example, in acase that the UE 102 detects (e.g., decode, receive) the DCI format forthe downlink including the priority indication, the UE 102 may identifythe PDSCH transmission and/or the PDSCH reception is prioritized (e.g.,the PDSCH transmission and/or the PDSCH reception has the higherpriority, the highest priority, the lower priority, and/or the lowestpriority).

Additionally or alternatively, the priority indication may be used forindicating a priority (e.g., 2-bit information, 00: the lowest priority,01: the lower priority, 10: the higher priority, and/or 11: the highestpriority) for the HARQ-ACK transmission for the PDSCH and/or theHARQ-ACK reception for the PDSCH. For example, in a case that the UE 102detects the DCI format for the downlink including the priorityindication, the UE 102 may identify the HARQ-ACK transmission for thePDSCH and/or the HARQ-ACK reception for the PDSCH is prioritized (e.g.,the HARQ-ACK transmission for the PDSCH and/or the HARQ-ACK receptionfor the PDSCH has the higher priority, the highest priority, the lowerpriority, and/or the lowest priority).

Additionally or alternatively, a DCI format 1_1 that is used forscheduling of the PDSCH in the cell may be defined as the DCI format forthe downlink. Additionally or alternatively, the C-RNTI, the CS-RNTI,and/or the first RNTI may be used to transmit the DCI format 1_1.Additionally or alternatively, the DCI format 1_1 may be monitored(e.g., transmitted and/or mapped) in the CSS and/or the USS.

For example, the DCI included in the DCI format 1_1 may be a BWPindicator (e.g., for the PDSCH). Additionally or alternatively, the DCIincluded in the DCI format 1_1 may be frequency domain resourceassignment (e.g., for the PDSCH). Additionally or alternatively, the DCIincluded in the DCI format 1_1 may be a time domain resource assignment(e.g., for the PDSCH). Additionally or alternatively, the DCI includedin the DCI format 1_1 may be a modulation and coding scheme (e.g., forthe PDSCH). Additionally or alternatively, the DCI included in the DCIformat 1_1 may be a new data indicator. Additionally or alternatively,the DCI included in the DCI format 1_1 may be a TPC command forscheduled PUCCH. Additionally or alternatively, the DCI included in theDCI format 1_1 may be a CSI request that is used for requesting (e.g.,triggering) transmission of the CSI (e.g., CSI reporting (e.g.,aperiodic CSI reporting)). Additionally or alternatively, the DCIincluded in the DCI format 1_1 may be a PUCCH resource indicator.Additionally or alternatively, the DCI included in the DCI format 1_1may be a PDSCH-to-HARQ feedback timing indicator. Additionally oralternatively, the DCI included in the DCI format 1_1 may be thepriority indication (e.g., for the PDSCH transmission and/or the PDSCHreception). Additionally or alternatively, the DCI included in the DCIformat 1_1 may be the priority indication (e.g., for the HARQ-ACKtransmission for the PDSCH and/or the HARQ-ACK reception for the PDSCH).

Additionally or alternatively, a DCI format 1_X that is used forscheduling of the PDSCH in the cell may be defined as the DCI format forthe downlink. Additionally or alternatively, the C-RNTI, the CS-RNTI,and/or the first RNTI may be used to transmit the DCI format 1_X.Additionally or alternatively, the DCI format 1_X may be monitored(e.g., transmitted and/or mapped) in the CSS and/or the USS.

For example, the DCI included in the DCI format 1_X may be a BWPindicator (e.g., for the PDSCH). Additionally or alternatively, the DCIincluded in the DCI format 1_X may be frequency domain resourceassignment (e.g., for the PDSCH). Additionally or alternatively, the DCIincluded in the DCI format 1_X may be a time domain resource assignment(e.g., for the PDSCH). Additionally or alternatively, the DCI includedin the DCI format 1_X may be a modulation and coding scheme (e.g., forthe PDSCH). Additionally or alternatively, the DCI included in the DCIformat 1_X may be a new data indicator. Additionally or alternatively,the DCI included in the DCI format 1_X may be a TPC command forscheduled PUCCH. Additionally or alternatively, the DCI included in theDCI format 1_X may be a CSI request that is used for requesting (e.g.,triggering) transmission of the CSI (e.g., CSI reporting (e.g.,aperiodic CSI reporting)). Additionally or alternatively, the DCIincluded in the DCI format 1_X may be a PUCCH resource indicator.Additionally or alternatively, the DCI included in the DCI format 1_Xmay be a PDSCH-to-HARQ feedback timing indicator. Additionally oralternatively, the DCI included in the DCI format 1_X may be thepriority indication (e.g., for the PDSCH transmission and/or the PDSCHreception). Additionally or alternatively, the DCI included in the DCIformat 1_X may be the priority indication (e.g., for the HARQ-ACKtransmission for the PDSCH and/or the HARQACK reception for the PDSCH).

Here, the DCI format 1_X (and/or the DCI format 1_X including thepriority indication) may be used for indicating a priority (e.g., thehigher priority, the highest priority, the lower priority, and/or thelowest priority) for the PDSCH transmission and/or the PDSCH reception.For example, in a case that the UE 102 detects the DCI format 1_X(and/or the DCI format 1_X including the priority indication), the UE102 may identify the PDSCH transmission and/or the PDSCH reception isprioritized (e.g., the PDSCH transmission and/or the PDSCH reception hasthe higher priority, the highest priority, the lower priority, and/orthe lowest priority).

Additionally or alternatively, the DCI format 1_X (and/or the DCI format1_X including the priority indication, and/or the DCI format 1_X withthe CRC scrambled by the first RNTI, and/or the DCI format 1_X with theCRC scrambled by the first RNTI including the priority indication) maybe used for indicating a priority (e.g., the higher priority, thehighest priority, the lower priority, and/or the lowest priority) forthe HARQ-ACK transmission for the PDSCH and/or the HARQ-ACK receptionfor the PDSCH. For example, in a case that the UE 102 detects the DCIformat 1_X (and/or the DCI format 1_X including the priority indication,and/or the DCI format 1_X with the CRC scrambled by the first RNTI,and/or the DCI format 1_X with the CRC scrambled by the first RNTIincluding the priority indication), the UE 102 may identify the HARQ-ACKtransmission for the PDSCH and/or the HARQ-ACK reception for the PDSCHis prioritized (e.g., the HARQ-ACK transmission for the PDSCH and/or theHARQ-ACK reception for the PDSCH has the higher priority, the highestpriority, the lower priority, and/or the lowest priority).

Additionally or alternatively, a DCI format 0_0 that is used forscheduling of the PUSCH in the cell may be defined as the DCI format forthe uplink. Additionally or alternatively, the C-RNTI, the CS-RNTI, theTemporary C-RNTI, and/or the first RNTI may be used to transmit the DCIformat 0_0. Additionally or alternatively, the DCI format 0_0 may bemonitored (e.g., transmitted, mapped) in the CSS and/or the USS.Alternatively, the DCI format 0_0 may be monitored (e.g., transmitted,mapped) in the CSS only.

For example, the DCI included in the DCI format 0_0 may be a frequencydomain resource assignment (e.g., for the PUSCH). Additionally oralternatively, the DCI included in the DCI format 0_0 may be a timedomain resource assignment (e.g., for the PUSCH). Additionally oralternatively, the DCI included in the DCI format 0_0 may be amodulation and coding scheme (e.g., for the PUSCH). Additionally oralternatively, the DCI included in the DCI format 0_0 may be a new dataindicator. Additionally or alternatively, the DCI included in the DCIformat 0_0 may be a redundancy version. Additionally or alternatively,the DCI included in the DCI format 0_0 may be a TPC command forscheduled PUSCH. Additionally or alternatively, the DCI included in theDCI format 0_0 may be the priority indication (e.g., for the PUSCHtransmission and/or for the PUSCH reception).

Here, the priority indication may be used for indicating a priority(e.g., 2-bit information, 00: the lowest priority, 01: the lowerpriority, 10: the higher priority, and/or 11: the highest priority) forthe PUSCH transmission and/or the PUSCH reception. For example, in acase that the UE 102 detects the DCI format for the uplink including thepriority indication, the UE 102 may identify the PUSCH transmissionand/or the PUSCH reception is prioritized (e.g., the PUSCH transmissionand/or the PUSCH reception has the higher priority, the highestpriority, the lower priority, and/or the lowest priority).

Additionally or alternatively, a DCI format 0_1 that is used forscheduling of the PUSCH in the cell may be defined as the DCI format forthe uplink. Additionally or alternatively, the C-RNTI, the CS-RNTIand/or the first RNTI may be used to transmit the DCI format 0_1.Additionally or alternatively, the DCI format 0_1 may be monitored(e.g., transmitted, mapped) in the CSS and/or the USS.

For example, the DCI included in the DCI format 0_1 may be a BWPindicator (e.g., for the PUSCH). Additionally or alternatively, the DCIincluded in the DCI format 0_1 may be a frequency domain resourceassignment (e.g., for the PUSCH). Additionally or alternatively, the DCIincluded in the DCI format 0_1 may be a time domain resource assignment(e.g., for the PUSCH). Additionally or alternatively, the DCI includedin the DCI format 0_1 may be a modulation and coding scheme (e.g., forthe PUSCH). Additionally or alternatively, the DCI included in the DCIformat 0_1 may be a new data indicator. Additionally or alternatively,the DCI included in the DCI format 0_1 may be a TPC command forscheduled PUSCH. Additionally or alternatively, the DCI included in theDCI format 0_1 may be a CSI request that is used for requesting the CSIreporting. Additionally or alternatively, as described below, the DCIincluded in the DCI format 0_1 may be information used for indicating anindex of a configuration of a configured grant. Additionally oralternatively, the DCI included in the DCI format 0_0 may be thepriority indication (e.g., for the PUSCH transmission and/or for thePUSCH reception).

Additionally or alternatively, a DCI format 0_Y that is used forscheduling of the PUSCH in the cell may be defined as the DCI format forthe uplink. Additionally or alternatively, the C-RNTI, the CS-RNTIand/or the first RNTI may be used to transmit the DCI format 0_Y.Additionally or alternatively, the DCI format 0_Y may be monitored(e.g., transmitted, mapped) in the CSS and/or the USS.

For example, the DCI included in the DCI format 0_Y may be a BWPindicator (e.g., for the PUSCH). Additionally or alternatively, the DCIincluded in the DCI format 0_Y may be a frequency domain resourceassignment (e.g., for the PUSCH). Additionally or alternatively, the DCIincluded in the DCI format 0_Y may be a time domain resource assignment(e.g., for the PUSCH). Additionally or alternatively, the DCI includedin the DCI format 0_Y may be a modulation and coding scheme (e.g., forthe PUSCH). Additionally or alternatively, the DCI included in the DCIformat 0_Y may be a new data indicator. Additionally or alternatively,the DCI included in the DCI format 0_Y may be a TPC command forscheduled PUSCH. Additionally or alternatively, the DCI included in theDCI format 0_Y may be a CSI request that is used for requesting the CSIreporting. Additionally or alternatively, as described below, the DCIincluded in the DCI format 0_Y may be information used for indicating anindex of a configuration of a configured grant. Additionally oralternatively, the DCI included in the DCI format 0_Y may be thepriority indication (e.g., for the PUSCH transmission and/or for thePUSCH reception).

Here, the DCI format 0_Y (and/or the DCI format 0_Y including thepriority indication, and/or the DCI format 0_Y with the CRC scrambled bythe first RNTI, and/or the DCI format 0_Y with the CRC scrambled by thefirst RNTI including the priority indication) may be used for indicatinga priority (e.g., the higher priority, the highest priority, the lowerpriority, and/or the lowest priority) for the PUSCH transmission and/orthe PUSCH reception. For example, in a case that the UE 102 detects theDCI format 0_Y (and/or the DCI format 0_Y including the priorityindication, and/or the DCI format 0_Y with the CRC scrambled by thefirst RNTI, and/or the DCI format 0_Y with the CRC scrambled by thefirst RNTI including the priority indication), the UE 102 may identifythe PUSCH transmission and/or the PUSCH reception is prioritized (e.g.,the PUSCH transmission and/or the PUSCH reception has the higherpriority, the highest priority, the lower priority, and/or the lowestpriority).

Additionally or alternatively, in a case that the DCI format 1_0, theDCI format 1_1 and/or the DCI format 1_X is received (e.g., based on thedetection of the DCI format 1_0, the DCI format 1_1, the DCI format1_X), the UE 102 may perform the PDSCH reception. Additionally oralternatively, in a case that the DCI format 0_0, the DCI format 0_1,and/or the DCI format 0_Y is received (e.g., based on the detection ofthe DCI format 0_0, the DCI format 0_1, and/or the DCI format 0_Y), theUE 102 may perform the PUSCH transmission.

Here, as described above, a RNTI(s) (e.g., a Radio Network TemporaryIdentifier(s)) assigned to the UE 102 may be used for transmission ofDCI (e.g., the DCI format(s), DL control channel(s) (e.g., thePDCCH(s)). Namely, the gNB 160 may transmit, (e.g., by using the RRCmessage), information used for configuring (e.g., assigning) the RNTI(s)to the UE 102.

For example, CRC (Cyclic Redundancy Check) parity bits (also referred tosimply as CRC), which are generated based on DCI, are attached to DCI,and, after attachment, the CRC parity bits are scrambled by the RNTI(s).The UE 102 may attempt to decode (e.g., blind decoding, monitor, detect)DCI to which the CRC parity bits scrambled by the RNTI(s) are attached.For example, the UE 102 detects DL control channel (e.g., the PDCCH, theDCI, the DCI format(s)) based on the blind decoding. That is, the UE 102may decode the DL control channel(s) with the CRC scrambled by theRNTI(s). In other words, the UE 102 may monitor the DL controlchannel(s) with the RNTI(s). For example, the UE 102 may detect the DCIformat(s) with the RNTI(s).

Here, the RNTI(s) may include the C-RNTI(s) (Cell-RNTI(s)), theCS-RNTI(s) (Configured Scheduling C-RNTI(s)), the SI-RNTI(s) (SystemInformation RNTI(s)), the RA-RNTI(s) (Random Access-RNTI(s)), theTemporary C-RNTI(s), and/or the first RNTI.

For example, the C-RNTI(s) may be a unique identification used foridentifying an RRC connection and/or scheduling. Additionally oralternatively, the CS-RNTI(s) may be a unique identification used forscheduling of transmission based on a configured grant. Additionally oralternatively, the SI-RNTI may be used for identifying systeminformation (SI) (e.g., an SI message) mapped on the BCCH anddynamically carried on DL-SCH. Additionally or alternatively, theSI-RNTI may be used for broadcasting of SI. Additionally oralternatively, the RA-RNTI may be an identification used for the randomaccess procedure (e.g., Msg.2 transmission). Additionally oralternatively, the Temporary C-RNTI may be used for the random accessprocedure (e.g., scheduling of Msg.3 (re)transmission (e.g., Msg.3 PUSCH(re)transmission)).

Here, in the random access procedure (e.g., a contention based randomaccess procedure), the Msg.3 PUSCH transmission (e.g., an initialtransmission) may be scheduled by using a random access response grant.For example, in the random access procedure, the random access responsegrant may be included in the PDSCH (e.g., the Msg.2 transmission). Also,in the random access procedure, the random access response grant may beused for scheduling of the PUSCH for the Msg. 3 transmission. Also, asdescribed above, the PDCCH (i.e., the DCI format 0_0) with the CRCscrambled by the Temporary C-RNTI may be used for scheduling of thePUSCH for the Msg. 3 transmission (e.g., Msg. 3 retransmission).

Additionally or alternatively, the first RNTI may be an identificationused for indicating a priority (e.g., the higher priority, the highestpriority, the lower priority, and/or the lowest priority) for the PDSCHtransmission and/or the PDSCH reception. For example, in a case that theUE 102 detects the PDCCH with the CRC scrambled by the first RNTI, theUE 102 may identify the corresponding PDSCH is prioritized (e.g., thecorresponding PDSCH transmission/reception has the higher priority, thehighest priority, the lower priority, and/or the lowest priority).

Additionally or alternatively, the first RNTI(s) may be anidentification used for indicating a priority (e.g., the higherpriority, the highest priority, the lower priority, and/or the lowestpriority) for the HARQ-ACK transmission for the PDSCH and/or theHARQ-ACK reception for the PDSCH. For example, in a case that the UE 102detects the PDCCH with the CRC scrambled by the first RNTI(s), the UE102 may identify the HARQ-ACK for the corresponding PDSCH is prioritized(e.g., the HARQ-ACK transmission/reception for the corresponding PDSCHhas the higher priority, the highest priority, the lower priority,and/or the lowest priority).

Additionally or alternatively, the first RNTI(s) may be anidentification used for indicating a priority (e.g., the higherpriority, the highest priority, the lower priority, and/or the lowestpriority) for the PUSCH transmission and/or the PUSCH reception. Forexample, in a case that the UE 102 detects the PDCCH with the CRCscrambled by the first RNTI, the UE 102 may identify the correspondingPUSCH is prioritized (e.g., the corresponding PUSCHtransmission/reception has the higher priority, the highest priority,the lower priority, and/or the lowest priority).

Additionally or alternatively, a physical downlink shared channel(PDSCH) and a physical uplink shared channel (PUSCH) may be defined. Forexample, in a case that the PDSCH (e.g., the PDSCH resource) isscheduled by using the DCI format(s) for the downlink, the UE 102 mayreceive the downlink data, on the scheduled PDSCH (e.g., the PDSCHresource). Additionally or alternatively, in a case that the PUSCH(e.g., the PUSCH resource) is scheduled by using the DCI format(s) forthe uplink, the UE 102 transmits the uplink data, on the scheduled PUSCH(e.g., the PUSCH resource). For example, the PDSCH may be used totransmit the downlink data (e.g., DL-SCH(s), a downlink transportblock(s)). Additionally or alternatively, the PUSCH may be used totransmit the uplink data (e.g., UL-SCH(s), an uplink transportblock(s)).

Furthermore, the PDSCH and/or the PUSCH may be used to transmitinformation of a higher layer (e.g., a radio resource control (RRC))layer, and/or a MAC layer). For example, the PDSCH (e.g., from the gNB160 to the UE 102) and/or the PUSCH (e.g., from the UE 102 to the gNB160) may be used to transmit a RRC message (a RRC signal). Additionallyor alternatively, the PDSCH (e.g., from the gNB 160 to the UE 102)and/or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used totransmit a MAC control element (a MAC CE). Here, the RRC message and/orthe MAC CE are also referred to as a higher layer signal.

In some approaches, a physical broadcast channel (PBCH) may be defined.For example, the PBCH may be used for broadcasting the MIB (masterinformation block). Here, system information may be divided into the MIBand a number of SIB(s) (system information block(s)). For example, theMIB may be used for carrying include minimum system information.Additionally or alternatively, the SIB(s) may be used for carryingsystem information messages.

In some approaches, in downlink, a SS (Synchronization Signal) may bedefined. The SS may be used for acquiring time and/or frequencysynchronization with a cell. Additionally or alternatively, the SS maybe used for detecting a physical layer cell ID of the cell.

In the radio communication for uplink, UL RS(s) may be used as uplinkphysical signal(s). Additionally or alternatively, in the radiocommunication for downlink, DL RS(s) may be used as downlink physicalsignal(s). The uplink physical signal(s) and/or the downlink physicalsignal(s) may not be used to transmit information that is provided fromthe higher layer, but is used by a physical layer.

Here, the downlink physical channel(s) and/or the downlink physicalsignal(s) described herein may be assumed to be included in a downlinksignal (e.g., a DL signal(s)) in some implementations for the sake ofsimple descriptions. Additionally or alternatively, the uplink physicalchannel(s) and/or the uplink physical signal(s) described herein may beassumed to be included in an uplink signal (i.e. an UL signal(s)) insome implementations for the sake of simple descriptions.

Also, in a carrier aggregation (CA), the gNB 160 and the UE 102 maycommunicate with each other using one or more serving cells. Here theone or more serving cells may include one primary cell and one or moresecondary cells. For example, the gNB 160 may transmit, by using the RRCmessage, information used for configuring one or more secondary cells toform together with the primary cell a set of serving cells. Namely, theset of serving cells may include one primary cell and one or moresecondary cells. Here, the primary cell may be always activated. Also,the gNB 160 may activate one or more secondary cell within theconfigured secondary cells. Here, in the downlink, a carriercorresponding to the primary cell may be the downlink primary componentcarrier (i.e., the DL PCC), and a carrier corresponding to a secondarycell may be the downlink secondary component carrier (i.e., the DL SCC).Also, in the uplink, a carrier corresponding to the primary cell may bethe uplink primary component carrier (i.e., the UL PCC), and a carriercorresponding to the secondary cell may be the uplink secondarycomponent carrier (i.e., the UL SCC).

The UE operations module 124 may provide information 148 to the one ormore receivers 120. For example, the UE operations module 124 may informthe receiver(s) 120 when to receive retransmissions.

The UE operations module 124 may provide information 138 to thedemodulator 114. For example, the UE operations module 124 may informthe demodulator 114 of a modulation pattern anticipated fortransmissions from the gNB 160.

The UE operations module 124 may provide information 136 to the decoder108. For example, the UE operations module 124 may inform the decoder108 of an anticipated encoding for transmissions from the gNB 160.

The UE operations module 124 may provide information 142 to the encoder150. The information 142 may include data to be encoded and/orinstructions for encoding. For example, the UE operations module 124 mayinstruct the encoder 150 to encode transmission data 146 and/or otherinformation 142. The other information 142 may include PDSCH HARQ-ACKinformation.

The encoder 150 may encode transmission data 146 and/or otherinformation 142 provided by the UE operations module 124. For example,encoding the data 146 and/or other information 142 may involve errordetection and/or correction coding, mapping data to space, time and/orfrequency resources for transmission, multiplexing, etc. The encoder 150may provide encoded data 152 to the modulator 154.

The UE operations module 124 may provide information 144 to themodulator 154. For example, the UE operations module 124 may inform themodulator 154 of a modulation type (e.g., constellation mapping) to beused for transmissions to the gNB 160. The modulator 154 may modulatethe encoded data 152 to provide one or more modulated signals 156 to theone or more transmitters 158.

The UE operations module 124 may provide information 140 to the one ormore transmitters 158. This information 140 may include instructions forthe one or more transmitters 158. For example, the UE operations module124 may instruct the one or more transmitters 158 when to transmit asignal to the gNB 160. For instance, the one or more transmitters 158may transmit during a UL subframe. The one or more transmitters 158 mayupconvert and transmit the modulated signal(s) 156 to one or more gNBs160.

Each of the one or more gNBs 160 may include one or more transceivers176, one or more demodulators 172, one or more decoders 166, one or moreencoders 109, one or more modulators 113, a data buffer 162 and a gNBoperations module 182. For example, one or more reception and/ortransmission paths may be implemented in a gNB 160. For convenience,only a single transceiver 176, decoder 166, demodulator 172, encoder 109and modulator 113 are illustrated in the gNB 160, though multipleparallel elements (e.g., transceivers 176, decoders 166, demodulators172, encoders 109 and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one ormore transmitters 117. The one or more receivers 178 may receive signalsfrom the UE 102 using one or more physical antennas 180 a-n. Forexample, the receiver 178 may receive and downconvert signals to produceone or more received signals 174. The one or more received signals 174may be provided to a demodulator 172. The one or more transmitters 117may transmit signals to the UE 102 using one or more physical antennas180 a-n. For example, the one or more transmitters 117 may upconvert andtransmit one or more modulated signals 115.

The demodulator 172 may demodulate the one or more received signals 174to produce one or more demodulated signals 170. The one or moredemodulated signals 170 may be provided to the decoder 166. The gNB 160may use the decoder 166 to decode signals. The decoder 166 may produceone or more decoded signals 164, 168. For example, a first eNB-decodedsignal 164 may comprise received payload data, which may be stored in adata buffer 162. A second eNB-decoded signal 168 may comprise overheaddata and/or control data. For example, the second eNB decoded signal 168may provide data (e.g., PDSCH HARQ-ACK information) that may be used bythe gNB operations module 182 to perform one or more operations.

In general, the gNB operations module 182 may enable the gNB 160 tocommunicate with the one or more UEs 102. The gNB operations module 182may include one or more of a gNB scheduling module 194. The gNBscheduling module 194 may perform scheduling of downlink and/or uplinktransmissions as described herein.

The gNB operations module 182 may provide information 188 to thedemodulator 172. For example, the gNB operations module 182 may informthe demodulator 172 of a modulation pattern anticipated fortransmissions from the UE(s) 102.

The gNB operations module 182 may provide information 186 to the decoder166. For example, the gNB operations module 182 may inform the decoder166 of an anticipated encoding for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 101 to the encoder109. The information 101 may include data to be encoded and/orinstructions for encoding. For example, the gNB operations module 182may instruct the encoder 109 to encode information 101, includingtransmission data 105.

The encoder 109 may encode transmission data 105 and/or otherinformation included in the information 101 provided by the gNBoperations module 182. For example, encoding the data 105 and/or otherinformation included in the information 101 may involve error detectionand/or correction coding, mapping data to space, time and/or frequencyresources for transmission, multiplexing, etc. The encoder 109 mayprovide encoded data 111 to the modulator 113. The transmission data 105may include network data to be relayed to the UE 102.

The gNB operations module 182 may provide information 103 to themodulator 113. This information 103 may include instructions for themodulator 113. For example, the gNB operations module 182 may inform themodulator 113 of a modulation type (e.g., constellation mapping) to beused for transmissions to the UE(s) 102. The modulator 113 may modulatethe encoded data 111 to provide one or more modulated signals 115 to theone or more transmitters 117.

The gNB operations module 182 may provide information 192 to the one ormore transmitters 117. This information 192 may include instructions forthe one or more transmitters 117. For example, the gNB operations module182 may instruct the one or more transmitters 117 when to (or when notto) transmit a signal to the UE(s) 102. The one or more transmitters 117may upconvert and transmit the modulated signal(s) 115 to one or moreUEs 102.

It should be noted that a DL subframe may be transmitted from the gNB160 to one or more UEs 102 and that a UL subframe may be transmittedfrom one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160and the one or more UEs 102 may transmit data in a standard specialsubframe.

It should also be noted that one or more of the elements or partsthereof included in the eNB(s) 160 and UE(s) 102 may be implemented inhardware. For example, one or more of these elements or parts thereofmay be implemented as a chip, circuitry or hardware components, etc. Itshould also be noted that one or more of the functions or methodsdescribed herein may be implemented in and/or performed using hardware.For example, one or more of the methods described herein may beimplemented in and/or realized using a chipset, an application-specificintegrated circuit (ASIC), a large-scale integrated circuit (LSI) orintegrated circuit, etc.

FIG. 2 shows examples of multiple numerologies 201. As shown in FIG. 2,multiple numerologies 201 (e.g., multiple subcarrier spacing) may besupported. For example, μ, (e.g., a subcarrier space configuration) anda cyclic prefix (e.g., the μ and the cyclic prefix for a carrierbandwidth part) may be configured by higher layer parameters (e.g., aRRC message) for the downlink and/or the uplink. Here, 15 kHz may be areference numerology 201. For example, an RE of the reference numerology201 may be defined with a subcarrier spacing of 15 kHz in a frequencydomain and 2048Ts+CP length (e.g., 160Ts or 144Ts) in a time domain,where Ts denotes a baseband sampling time unit defined as 1/(15000*2048)seconds.

Additionally or alternatively, a number of OFDM symbol(s) 203 per slot(N_(symb) ^(slot)) may be determined based on the μ (e.g., thesubcarrier space configuration). Here, for example, a slot configuration0 (e.g., the number of OFDM symbols 203 per slot may be 14) and/or aslot configuration (e.g., the number of OFDM symbols 203 per slot may be7) may be defined. FIG. 3 is a diagram illustrating one example of aresource grid 301 and resource block 391 (e.g., for the downlink and/orthe uplink). The resource grid 301 and resource block 391 illustrated inFIG. 3 may be utilized in some implementations of the systems andmethods disclosed herein.

In FIG. 3, one subframe 369 may include N_(symbol) ^(subframe,μ) symbols387. Additionally or alternatively, a resource block 391 may include anumber of resource elements (RE) 389. Here, in the downlink, the OFDMaccess scheme with cyclic prefix (CP) may be employed, which may be alsoreferred to as CP-OFDM. A downlink radio frame may include multiplepairs of downlink resource blocks (RBs) 391 which is also referred to asphysical resource blocks (PRBs). The downlink RB pair is a unit forassigning downlink radio resources, defined by a predetermined bandwidth(RB bandwidth) and a time slot. The downlink RB pair may include twodownlink RBs 391 that are continuous in the time domain. Additionally oralternatively, the downlink RB 391 may include twelve sub-carriers infrequency domain and seven (for normal CP) or six (for extended CP) OFDMsymbols in time domain. A region defined by one sub-carrier in frequencydomain and one OFDM symbol in time domain is referred to as a resourceelement (RE) 389 and is uniquely identified by the index pair (k,l),where k and l are indices in the frequency and time domains,respectively.

Additionally or alternatively, in the uplink, in addition to CP-OFDM, aSingle-Carrier Frequency Division Multiple Access (SC-FDMA) accessscheme may be employed, which is also referred to as Discrete FourierTransform-Spreading OFDM (DFT-S-OFDM). An uplink radio frame may includemultiple pairs of uplink resource blocks 391. The uplink RB pair is aunit for assigning uplink radio resources, defined by a predeterminedbandwidth (RB bandwidth) and a time slot. The uplink RB pair may includetwo uplink RBs 391 that are continuous in the time domain. The uplink RBmay include twelve sub-carriers in frequency domain and seven (fornormal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbols in timedomain. A region defined by one sub-carrier in the frequency domain andone OFDM/DFT-S-OFDM symbol in the time domain is referred to as aresource element (RE) 389 and is uniquely identified by the index pair(k,l) in a slot, where k and l are indices in the frequency and timedomains respectively.

Each element in the resource grid 301 (e.g., antenna port p) and thesubcarrier configuration p is called a resource element 389 and isuniquely identified by the index pair (k, l) where k=0, . . . , N_(RB)^(μ)N_(SC) ^(RB)−1 is the index in the frequency domain and l refers tothe symbol position in the time domain. The resource element (k,l) 389on the antenna port p and the subcarrier spacing configuration μ isdenoted (k,l)_(p),μ. The physical resource block 391 is defined asN_(SC) ^(RB)=12 consecutive subcarriers in the frequency domain. Thephysical resource blocks 391 are numbered from 0 to N_(RB) ^(μ)−1 in thefrequency domain.

The relation between the physical resource block number ^(n)PRB in thefrequency domain and the resource element (k,l) is given by

$n_{PRB} = {\left\lfloor \frac{k}{N_{SC}^{RB}} \right\rfloor.}$

FIG. 4 shows examples of resource regions (e.g., resource region of thedownlink). One or more sets 401 of PRB(s) 491 (e.g., a control resourceset (e.g., CORESET)) may be configured for DL control channel monitoring(e.g., the PDCCH monitoring). For example, the CORESET is, in thefrequency domain and/or the time domain, a set 401 of PRBs 491 withinwhich the UE 102 attempts to decode the DCI (e.g., the DCI format(s),the PDCCH(s)), where the PRBs 491 may or may not be frequency contiguousand/or time contiguous, a UE 102 may be configured with one or morecontrol resource sets (e.g., the CORESETs) and one DCI message may bemapped within one control resource set. In the frequency-domain, a PRB491 is the resource unit size (which may or may not include DMRS) forthe DL control channel.

The UE 102 may monitor a set of candidates of the PDCCH in one or morecontrol resource sets (e.g., CORESETs) on the active DL bandwidth part(BWP) on each activated serving cell according to corresponding searchspace sets. Here, the term “monitor” may imply that the UE 102 attemptsto decode each PDCCH (e.g., the set of candidates of the PDCCH)according to the monitored DCI format(s). Also, the candidates of thePDCCH may be candidates for which the DL control channel(s) may possiblybe mapped, assigned, and/or transmitted.

The set of candidates of the PDCCH for the UE 102 to monitor may bedefined in terms of a search space set(s) (e.g., also referred to simplyas a search space(s)). The UE 102 may monitor the set of candidates ofthe PDCCH in the search space(s). The search space set(s) may comprise acommon search space(s) (CSS(s), UE-common search space(s)) and/or a userequipment-specific search space(s) (USS, UE-specific search space(s)).

Namely, the CSS and/or the USS may be defined (e.g., configured) in aregion(s) of DL control channel(s). For example, the CSS may be used fortransmission of DCI to a plurality of the UEs 102. For example, aType0-PDCCH common search space may be defined for the DCI format(s)with CRC scrambled by the SI-RNTI. Additionally or alternatively, aType1-PDCCH common search space may be defined for the DCI format(s)with CRC scrambled by the RA-RNTI, the Temporary C-RNTI, and/or theC-RNTI. Additionally or alternatively, a Type3-PDCCH common search spacemay be defined for the DCI format(s) with CRC scrambled by the C-RNTI,and/or the CS-RNTI.

The USS may be used for transmission of DCI to a specific UE 102. Forexample, the USS may be determined based on a Radio Network TemporaryIdentifier (RNTI) (e.g., the C-RNTI). For instance, the USS may bedefined for the DCI format(s) with CRC scrambled by the C-RNTI, and/orthe CS-RNTI.

Here, the gNB 160 may transmit, by using the RRC message, firstinformation used for configuring (e.g., determining) one or moreCORESETs. For example, for each of DL BWPs (e.g., each of DL BWPs in theserving cell), the gNB 106 may transmit, by using the RRC message, thefirst information used for configuring the one or more CORESET. Forexample, the first information may include information used forconfiguring an index of the CORESET. Also, the first information mayinclude information used for configuring a number of consecutive symbolsfor the CORESET. Also, the first information may include informationused for configuring a set of resource blocks for the CORESET.

Here, the index “0” of the CORESET (i.e., a value “0” of the CORESET)may be configured by using the MIB and/or the SIB(s). For example, theindex “0” of the CORESET may be used for identifying a common CORESETconfigured in the MIB and/or the SIB(s). Namely, the index of theCORESET except for the value “0” may be configured as the index of theCORESET. Also, the index of the CORESET with the value “0” may beconfigured by using information of a CORESET-zero. Also, the index “0”of the CORESET may be configured by using a dedicated RRC message (i.e.,a UE-specific RRC message, and/or a serving cell-specific RRC message).Namely, the gNB 160 may transmit, by using the MIB, information used forconfiguring the CORESET with the index “0” (i.e., a CORESET #0).Additionally or alternatively, the gNB 160 may transmit, by using theSIB(s), the information used for configuring the CORESET #0.Additionally or alternatively, the gNB 160 may transmit, by using thededicated RRC message, the information used for configuring the CORESET#0.

Here, the CORESET #0 may be configured for an initial BWP(s) (e.g., theinitial DL BWP(s)). Here, the gNB 160 may transmit, by using the RRCmessage (e.g., the MIB, the SIB(s), and/or the dedicated RRC message),information used for the initial BWP(s) (e.g., the initial BWP(s)).Also, an index of the initial BWP(s) (e.g., the initial DL BWP(s)) maybe “0”. Namely, the index “0” (e.g., the value “0”) may be applied(e.g., defined) for the initial BWP(s) (e.g., the initial DL BWP(s)).For example, (e.g., for the primary cell), the initial BWP(s) (i.e., theBWP with the index “0”) may be the BWP(s) used for an initial access.Additionally or alternately, (e.g., for the secondary cell(s)), theinitial BWP(s) (i.e., the BWP(s) with the index “0”) may be the BWP(s)configured for the UE to first operate at the secondary cell(s)activation.

Here, the gNB 106 may transmit, by using the RRC message (e.g., the MIB,the SIB(s), and/or the dedicated RRC message), information used forconfiguring an index of the DL BWP(s) (e.g., the index other than theindex “0”). Also, the gNB 106 may transmit, by using the RRC message(e.g., the MIB, the SIB(s), and/or the dedicated RRC message),information used for configuring an index of the UL BWP(s) (e.g., theindex other than the index “0”).

As described above, the CORESET#0 may be referred to as the commonCORESET. Also, the CORESET other than the CORESET#0 may be referred toas a UE-specific CORESET. Namely, the CORESET with the index “X (e.g.,X=1, 2, 3, . . . )” other than the index “0” may be referred to as theUE-specific CORESET. For example, the gNB 160 may transmit, by using thededicated RRC message, information used for configuring the UE-specificCORESET (e.g., the index of the UE-specific CORESET).

Additionally or alternatively, for each of the one or more CORESETs, thesearch space set(s) (e.g., the set(s) of the CSS(s) and/or the USS(s))may be configured. For example, the first information may be configuredper DL BWP. Namely, the first information may be configured for each ofthe DL BWPs in the serving cell.

Additionally or alternatively, the gNB 160 may transmit, by using theRRC message, second information used for configuring the search spaceset(s). For example, the second information may be configured for eachsearch space set. For example, the second information may includeinformation used for configuring an index of the search space set(s).Additionally or alternatively, the second information may includeinformation used for configuring the index of the CORESET(s) associatedwith the search space set(s). Additionally or alternatively, the secondinformation may include information used for indicating a PDCCHmonitoring periodicity and/or a PDCCH monitoring offset where the UE 102monitors the PDCCH(s) in the search space set(s). Additionally oralternatively, the second information may include information used forindicating a PDCCH monitoring pattern within a slot. For example, theinformation used for indicating the PDCCH monitoring pattern may be usedfor indicating first symbol(s) within a slot for the PDCCH monitoring.For instance, the UE 102 may determine a PDCCH monitoring occasion(s)based on the PDCCH monitoring periodicity, the PDCCH monitoring offset,and/or the PDCCH monitoring pattern within a slot.

Additionally or alternatively, the second information may includeinformation used for indicating a type of the search space set (e.g.,information used for indicating that the search space set is either theCSS or the USS). Additionally or alternatively, the second informationmay include information used for indicating one or more DCI formatswhich accordingly the UE 102 monitors the PDCCH in the search spaceset(s). For example, if the search space set is the CSS (e.g., if thesearch space set is configured as the CSS), the DCI format 0_0 and/orthe DCI format 1_0 may be configured to monitor the PDCCH (e.g., thecandidate(s) of the PDCCH(s)). Here, the DCI format(s) for monitoringthe PDCCH in the CSS may be scrambled by the CRNTI, the CS-RNTI, theRA-RNTI, the Temporary C-RNTI, the SI-RNTI, and/or the first RNTI.

Additionally or alternatively, if the search space set is the USS (e.g.,if the search space set is configured as the USS), the DCI format 0_0,the DCI format 1_0, the DCI format 0_Y, and/or the DCI format 1_X may beconfigured to monitor the PDCCH (e.g., the candidate(s) of thePDCCH(s)). Additionally or alternatively, if the search space set is theUSS, the DCI format 0_1, the DCI format 1_1, the DCI format 0_Y, and/orthe DCI format 1_X may be configured to monitor the PDCCH (e.g., thecandidate(s) of the PDCCH(s)). For example, if the search space set isthe USS, either of a first set of DCI formats (e.g., the DCI format 0_0,the DCI format 1_0, and/or the DCI format 0_Y, and/or the DCI format1_X) or a second set of DCI formats (e.g., the DCI format 0_1, the DCIformat 1_1, the DCI format 0_Y, and/or the DCI format 1_X) may beconfigured to monitor the PDCCH (e.g., the candidate(s) of thePDCCH(s)). Here, the DCI format(s) for monitoring the PDCCH in the USSmay be scrambled by the C-RNTI, the CS-RNTI, and/or the first RNTI. Forexample, the second information may be configured per search space set.Namely, the second information may be configured for each of searchspace sets.

Here, the index “0” of the search space set (i.e., a value “0” of thesearch space set) may be configured by using the MIB and/or the SIB(s).For example, the index “0” of the search space set may be used foridentifying a common search space set configured in the MIB and/or theSIB(s). Namely, the index of the search space set except for the value“0” may be configured as the index of the search space. Also, the indexof the search space set with the value “0” may be configured by usinginformation of search space-zero. Also, the index “0” of the searchspace set may be configured by using a dedicated RRC message (i.e., aUE-specific RRC message, and/or a serving cell-specific RRC message).Namely, the gNB 160 may transmit, by using the MIB, information used forconfiguring the search space set with the index “0” (i.e., the searchspace set #0). Additionally or alternatively, the gNB 160 may transmit,by using the SIB(s), the information used for configuring the searchspace set #0. Additionally or alternatively, the gNB 160 may transmit,by using the dedicated RRC message, the information used for configuringthe search space set #0. Here, the search space set #0 may be configuredfor the initial BWP(s) (e.g., the initial DL BWP(s)).

As described above, the search space set #0 may be referred to as thecommon search space set. Also, the search space set other than thesearch space set #0 may be referred to as a UE-specific search spaceset. Namely, the search space set with the index “X (e.g., X=1, 2, 3, .. . )” other than the index “0” may be referred to as the UE-specificsearch space set. For example, the gNB 160 may transmit, by using thededicated RRC message, information used for configuring the UE-specificsearch space set (e.g., the index of the UE-specific search space set).

Here, for example, for the serving cell(s), the gNB 160 may configure,by using the RRC message, a set of four DL BWPs (e.g., at most four DLBWPs, a DL BWP set) (e.g., for receptions by the UE 102). Additionallyor alternatively, the gNB 160 may indicate, by using the DCI format(s)for the downlink, an active DL BWP(s). For example, for each DL BWP inthe set of DL BWPs, the gNB 160 may configure, by using the RRC message,the subcarrier spacing, the cyclic prefix, a number of contiguous PRBs491 (e.g., a bandwidth of PRBs), and/or an index (e.g., the index of theDL BWP(s)) in the set of DL BWPs.

Additionally or alternatively, for the serving cell(s), the gNB 160 mayconfigure, by using the RRC message, a set of four UL BWP(s) (e.g., atmost four UL BWPs, a UL BWP set) (e.g., for transmissions by the UE102). Additionally or alternatively, the gNB 160 may indicate, by usingthe DCI format(s) for the uplink, an active UL BWP(s). Additionally oralternatively, for each UL BWP in the set of UL BWPs, the gNB 160 mayconfigure, by using the RRC message, the subcarrier spacing, the cyclicprefix, a number of contiguous PRBs 491 (e.g., a bandwidth of PRBs), anindex (e.g., the index of the UL BWP(s)) in the set of UL BWPs.

Additionally or alternatively, the UE 102 may perform, based on theconfiguration(s) for the DL BWP(s), reception(s) on the PDCCH in the DLBWP(s) and/or reception(s) on the PDSCH in the DL BWP(s). Additionallyor alternatively, the UE 102 may perform, based on the configuration(s)for the UL BWP(s).

FIG. 5 shows an example of the mini-slot repetition and multi-segmenttransmissions. This figure illustrates one or more actual PUSCHrepetitions (501 a, 501 b, and 501 c) in one slot (this may be referredto as “mini-slot repetition”) and/or two or more actual PUSCHrepetitions (502 a and 502 b) across slot boundary in consecutiveavailable slots (this may be referred to as “multi-segmenttransmission”) that are supported using one UL grant for dynamic PUSCHscheduled by DCI, and one configured grant configuration for configuredgrant PUSCH. Here, dynamic PUSCH may be a PUSCH scheduled by DCI on aPDCCH and a configured grant PUSCH may be referred to as type 1 or type2 configured grant scheduling. A configured grant configuration may be aPUSCH transmission resource (e.g., periodicity, the number ofrepetitions, etc.) configured by RRC. For type 1 configured grant, a UE102 may transmit a PUSCH according to RRC configuration. For type 2configured grant, a UE 102 may transmit a PUSCH according to RRC afterDCI activates the transmission of a PUSCH and until DCI deactivates thetransmission of a PUSCH. Mini-slot may be referred to as “PUSCH mappingtype B.” 503 a, 503 b, 503 c, 503 d, and 503 e are DMRS symbols and eachof the DMRS symbols may be mapped to the first OFDM symbol within amini-slot and/or a segment.

In this example depicted in FIG. 5, the number of repetitions(represented by K in this disclosure) is 4 and the number of OFDMsymbols scheduled for a PUSCH (represented by L in this disclosure) is4. In this case, the total number of OFDM symbols including repetitionsare K*L=16. The first repetition is 501 a, the second repetition is 501b, the third repetition is 502 a and 502 b, and the fourth repetition is501 c. In addition, in this example, the start OFDM symbol index(represented by S in this disclosure) is S=4, where OFDM symbols areindexed 0, 1, . . . , 13 within a slot. As show in this figure, the 3rdrepetition is mapped across slot boundary, and this repetition is splitinto two segments 502 a and 502 b.

As another example, FIG. 6 illustrates an example of multi-segmenttransmission. In this case, the number of repetition K is 1 but thenumber of scheduled OFDM symbols (L) is 14 and start OFDM symbol index(S) of the scheduled PUSCH is 4. And a PUSCH is split into two segments601 a and 601 b. Even in case of K=1, if S+L>14, a UE 102 may transmit aPUSCH with multi-segment transmission as shown in FIGS. 6. 603 a and 603b are DMRS symbols and each of the DMRS symbols may be mapped to thefirst OFDM symbol within a segment.

As another example, FIG. 7 illustrates another example of mini-slotrepetition transmission. In this case, the number of repetition K is 2,and the number of scheduled OFDM symbols (L) is 4 and start OFDM symbolindex (S) of the scheduled PUSCH is 4. This figure illustrates PUSCHrepetitions (701 a and 701 b) in one slot. 703 a and 703 b are DMRSsymbols and each of the DMRS symbols may be mapped to the first OFDMsymbol within a segment.

When DCI scheduled a PUSCH, the DCI may include the number of scheduledOFDM symbols (L) of the first repetition (501 a in FIG. 5 and the sum ofOFDM symbols of 601 a and 602 b). The DCI may include the number ofrepetitions (K). The DCI may include the combination of the start OFDMsymbol index and the number of scheduled OFDM symbols (this is referredto as SLIV (Start and Length Indicator Value)).

How to determine a transport block size (TBS) is also described herein.The TBS may be the size of the data bits (UL-SCH bits) transferred fromthe MAC layer. The TBS may be determined by the number of resourceelements (REs) for DMRS symbols, the number of REs as overheadconfigured by RRC, the number of scheduled OFDM symbols, and/or thenumber of scheduled physical resource blocks (PRBs).

The TBS may be determined by the number of OFDM symbols indicated by anSLIV field in DCI. Alternately, the TBS may be determined by the minimumnumber of OFDM symbols of mini-slots and/or segments scheduled in thetime domain. For example, in FIG. 5, the numbers of OFDM symbols foreach mini-slot or each segment are 4 for a mini-slot 501 a, 4 for amini-slot 501 b, 2 for a segment 502 a, 2 for a segment 502 b, and 4 fora mini-slot 501 b symbols. In this case, the number of OFDM symbols todetermine the TBS is 4. Alternately, in FIG. 5, the number of OFDMsymbols to determine the TBS of the 3rd repetition may be 4.

Alternately or additionally, for the multi-segment transmission acrossslot boundary, when a UE 102 determines the TBS for the 3rd repetition(for segments 502 a and 502 b), the UE 102 may use both the number ofDMRS symbols of the 1st segment (502 a) and the number of DMRS symbolsof the 2nd segment (502 b). For example, in the FIG. 5 case, a UE 102 isconfigured with one OFDM symbol for DMRS and additional DMRS are notconfigured. In this case, for the TBS calculation for the 1st, 2nd, and4th repetition, the number OFDM symbols of the DMRS that the UE 102 mayuse is one. However, for the TBS calculation for multi-segmenttransmission, the DMRS symbols are mapped on two time resources acrossthe slot boundary. Therefore, the TBS may be calculated by using 2 OFDMsymbols for the DMRS symbol(s) for each segment. Furthermore, when thenumber of REs of DMRS symbols configured and/or indicated for a PUSCHtransmission is N_(DMRS_RE) and the number of slots for a multi-segmenttransmission is N_(slot_seg), the number of OFDM symbols to calculatethe TBS may be N_(DMRS_RE)*N_(slot_seg). When a UE 102 calculates theTBS, the DMRS symbols added by the multi-segment transmission (onerepetition across slot boundary) may be used in addition to the DMRSconfiguration (type 1 or type 2) and additional DMRS. As another word,the number of REs of DMRS may be defined as the number of REs for DMRSper PRB in the scheduled duration including the overhead of the DMRS CDM(code division multiplexing) groups without data, as indicated by DCIformat 1_1 or as described for format 1_0. The CDM group may be definedthe DMRS RE group whose REs are not used to map the UL-SCH data.

Alternately or additionally, the maximum number of DMRS REs of all therepetitions may be used to calculate TBS.

In the above examples, this disclosure discloses that the number ofrepetitions and SLIV are indicated by the DCI. Alternately, thecombination of the number of repetitions and the time domain resourceallocation for each value of SLIV field may be configured by RRC.

FIG. 8 illustrates various components that may be utilized in a UE 802.The UE 802 described in connection with FIG. 8 may be implemented inaccordance with the UE 102 described in connection with FIG. 1. The UE802 includes a processor 803 that controls operation of the UE 802. Theprocessor 803 may also be referred to as a central processing unit(CPU). Memory 805, which may include read-only memory (ROM), randomaccess memory (RAM), a combination of the two or any type of device thatmay store information, provides instructions 807 a and data 809 a to theprocessor 803. A portion of the memory 805 may also include non-volatilerandom access memory (NVRAM). Instructions 807 b and data 809 b may alsoreside in the processor 803. Instructions 807 b and/or data 809 b loadedinto the processor 803 may also include instructions 807 a and/or data809 a from memory 805 that were loaded for execution or processing bythe processor 803. The instructions 807 b may be executed by theprocessor 803 to implement the methods described herein.

The UE 802 may also include a housing that contains one or moretransmitters 858 and one or more receivers 820 to allow transmission andreception of data. The transmitter(s) 858 and receiver(s) 820 may becombined into one or more transceivers 818. One or more antennas 822 a-nare attached to the housing and electrically coupled to the transceiver818.

The various components of the UE 802 are coupled together by a bussystem 811, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 8 as the bus system811. The UE 802 may also include a digital signal processor (DSP) 813for use in processing signals. The UE 802 may also include acommunications interface 815 that provides user access to the functionsof the UE 802. The UE 802 illustrated in FIG. 8 is a functional blockdiagram rather than a listing of specific components.

FIG. 9 illustrates various components that may be utilized in a gNB 960.The gNB 960 described in connection with FIG. 9 may be implemented inaccordance with the gNB 160 described in connection with FIG. 1. The gNB960 includes a processor 903 that controls operation of the gNB 960. Theprocessor 903 may also be referred to as a central processing unit(CPU). Memory 905, which may include read-only memory (ROM), randomaccess memory (RAM), a combination of the two or any type of device thatmay store information, provides instructions 907 a and data 909 a to theprocessor 903. A portion of the memory 905 may also include non-volatilerandom access memory (NVRAM). Instructions 907 b and data 909 b may alsoreside in the processor 903. Instructions 907 b and/or data 909 b loadedinto the processor 903 may also include instructions 907 a and/or data909 a from memory 905 that were loaded for execution or processing bythe processor 903. The instructions 907 b may be executed by theprocessor 903 to implement the methods described herein.

The gNB 960 may also include a housing that contains one or moretransmitters 917 and one or more receivers 978 to allow transmission andreception of data. The transmitter(s) 917 and receiver(s) 978 may becombined into one or more transceivers 976. One or more antennas 980 a-nare attached to the housing and electrically coupled to the transceiver976.

The various components of the gNB 960 are coupled together by a bussystem 911, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 9 as the bus system911. The gNB 960 may also include a digital signal processor (DSP) 913for use in processing signals. The gNB 960 may also include acommunications interface 915 that provides user access to the functionsof the gNB 960. The gNB 960 illustrated in FIG. 9 is a functional blockdiagram rather than a listing of specific components.

FIG. 10 is a block diagram illustrating one implementation of a UE 1002in which one or more of the systems and/or methods described herein maybe implemented. The UE 1002 includes transmit means 1058, receive means1020 and control means 1024. The transmit means 1058, receive means 1020and control means 1024 may be configured to perform one or more of thefunctions described in connection with FIG. 1 above. FIG. 8 aboveillustrates one example of a concrete apparatus structure of FIG. 10.Other various structures may be implemented to realize one or more ofthe functions of FIG. 1. For example, a DSP may be realized by software.

FIG. 11 is a block diagram illustrating one implementation of a gNB 1160in which one or more of the systems and/or methods described herein maybe implemented. The gNB 1160 includes transmit means 1117, receive means1178 and control means 1182. The transmit means 1117, receive means 1178and control means 1182 may be configured to perform one or more of thefunctions described in connection with FIG. 1 above. FIG. 9 aboveillustrates one example of a concrete apparatus structure of FIG. 11.Other various structures may be implemented to realize one or more ofthe functions of FIG. 1. For example, a DSP may be realized by software.

FIG. 12 is a block diagram illustrating one implementation of a gNB1260. The gNB 1260 may be an example of the gNB 160 described inconnection with FIG. 1. The gNB 1260 may include a higher layerprocessor 1223, a DL transmitter 1225, a UL receiver 1233, and one ormore antenna 1231. The DL transmitter 1225 may include a PDCCHtransmitter 1227 and a PDSCH transmitter 1229. The UL receiver 1233 mayinclude a PUCCH receiver 1235 and a PUSCH receiver 1237.

The higher layer processor 1223 may manage physical layer's behaviors(the DL transmitter's and the UL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1223 may obtain transport blocks from the physical layer. Thehigher layer processor 1223 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1223 may provide the PDSCH transmitter transportblocks and provide the PDCCH transmitter transmission parameters relatedto the transport blocks.

The DL transmitter 1225 may multiplex downlink physical channels anddownlink physical signals (including reservation signal) and transmitthem via transmission antennas 1231. The UL receiver 1233 may receivemultiplexed uplink physical channels and uplink physical signals viareceiving antennas 1231 and de-multiplex them. The PUCCH receiver 1235may provide the higher layer processor 1223 UCI. The PUSCH receiver 1237may provide the higher layer processor 1223 received transport blocks.

FIG. 13 is a block diagram illustrating one implementation of a UE 1302.The UE 1302 may be an example of the UE 102 described in connection withFIG. 1. The UE 1302 may include a higher layer processor 1323, a ULtransmitter 1351, a DL receiver 1343, and one or more antenna 1331. TheUL transmitter 1351 may include a PUCCH transmitter 1353 and a PUSCHtransmitter 1355. The DL receiver 1343 may include a PDCCH receiver 1345and a PDSCH receiver 1347.

The higher layer processor 1323 may manage physical layer's behaviors(the UL transmitter's and the DL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1323 may obtain transport blocks from the physical layer. Thehigher layer processor 1323 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1323 may provide the PUSCH transmitter transportblocks and provide the PUCCH transmitter 1353 UCI.

The DL receiver 1343 may receive multiplexed downlink physical channelsand downlink physical signals via receiving antennas 1331 andde-multiplex them. The PDCCH receiver 1345 may provide the higher layerprocessor 1323 DCI. The PDSCH receiver 1347 may provide the higher layerprocessor 1323 received transport blocks.

FIG. 14 is a flow diagram illustrating a communication method 1400 by aUE 102. The UE 102 may receive 1402 resource allocation information of aphysical uplink shared channel (PUSCH) and a number of repetitions forthe PUSCH. The UE 102 may calculate 1404 a transport block size (TBS)for the PUSCH. The UE 102 may transmit 1406 the PUSCH. The TBS may becalculated based on a number of resource elements (REs) for ademodulation reference signal (DMRS), REs for additional DMRS, and REsfor a DMRS added right after a slot boundary for a repetition of thePUSCH.

FIG. 15 is a flow diagram illustrating a communication method 1500 by abase station apparatus (gNB) 160. The gNB 160 may transmit 1502 resourceallocation information of a physical uplink shared channel (PUSCH) and anumber of repetitions for the PUSCH. The gNB 160 may receive 1504 thePUSCH. The TBS may be calculated based on a number of resource elements(REs) for a demodulation reference signal (DMRS), REs for additionalDMRS, and REs for a DMRS added right after a slot boundary for arepetition of the PUSCH.

FIG. 16 illustrates an example of the mini-slot repetition and/ormulti-segment transmission. FIG. 16 depicts an uplink slot 1603, fourDMRSs 1602 a-d and four PUSCHs 1601 a-d. Mini-slot may be called PUSCHmapping type B. Within an uplink slot 1603, two mini-slots are repeated(retransmitted). In the slot boundary, two minislots are transmitted(repeated) across the slot (two-segment transmission).

As shown in FIG. 16, four DMRSs 1602 a-d are transmitted. The UCI can bemapped around one or multiple DMRS. A UE 102 may transmit HARQ-ACK bitsby mapping HARQ-ACK bits right after the earliest DMRS equal to orgreater than the HARQ-ACK timing indicated by DCI or RRC signaling. Forexample, if the HARQ-ACK timing indicated by DCI or RRC signaling isequal to the middle of PUSCH 1601 a, the UCI is mapped on the resourceelements (REs) in an OFDM symbol right after DMRS 1602 b. The value ofthe beta_offset and alpha (α) may determine the number of REs.

As described herein, some methods for the UL transmissions may beapplied (e.g., specified). Here, the combination of one or more of thesome methods described herein may be applied for the UL transmission.The combination of the one or more of the some methods described hereinmay not be precluded in the described systems and methods.

It should be noted that names of physical channels described herein areexamples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH andNRPUSCH,” “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or thelike can be used.

The term “computer-readable medium” refers to any available medium thatcan be accessed by a computer or a processor. The term“computer-readable medium,” as used herein, may denote a computer-and/or processor-readable medium that is non-transitory and tangible. Byway of example and not limitation, a computer-readable orprocessor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer or processor. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray® disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.

It should be noted that one or more of the methods described herein maybe implemented in and/or performed using hardware. For example, one ormore of the methods described herein may be implemented in and/orrealized using a chipset, an application-specific integrated circuit(ASIC), a large-scale integrated circuit (LSI) or integrated circuit,etc.

Each of the methods disclosed herein comprises one or more steps oractions for achieving the described method. The method steps and/oractions may be interchanged with one another and/or combined into asingle step without departing from the scope of the claims. In otherwords, unless a specific order of steps or actions is required forproper operation of the method that is being described, the order and/oruse of specific steps and/or actions may be modified without departingfrom the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods and apparatus described herein withoutdeparting from the scope of the claims.

A program running on the gNB 160 or the UE 102 according to thedescribed systems and methods is a program (a program for causing acomputer to operate) that controls a CPU and the like in such a manneras to realize the function according to the described systems andmethods. Then, the information that is handled in these apparatuses istemporarily stored in a RAM while being processed. Thereafter, theinformation is stored in various ROMs or HDDs, and whenever necessary,is read by the CPU to be modified or written. As a recording medium onwhich the program is stored, among a semiconductor (for example, a ROM,a nonvolatile memory card, and the like), an optical storage medium (forexample, a DVD, a MO, a MD, a CD, a BD and the like), a magnetic storagemedium (for example, a magnetic tape, a flexible disk and the like) andthe like, any one may be possible. Furthermore, in some cases, thefunction according to the described systems and methods described hereinis realized by running the loaded program, and in addition, the functionaccording to the described systems and methods is realized inconjunction with an operating system or other application programs,based on an instruction from the program.

Furthermore, in a case where the programs are available on the market,the program stored on a portable recording medium can be distributed orthe program can be transmitted to a server computer that connectsthrough a network such as the Internet. In this case, a storage devicein the server computer also is included. Furthermore, some or all of thegNB 160 and the UE 102 according to the systems and methods describedherein may be realized as an LSI that is a typical integrated circuit.Each functional block of the gNB 160 and the UE 102 may be individuallybuilt into a chip, and some or all functional blocks may be integratedinto a chip. Furthermore, a technique of the integrated circuit is notlimited to the LSI, and an integrated circuit for the functional blockmay be realized with a dedicated circuit or a general-purpose processor.Furthermore, if with advances in a semiconductor technology, atechnology of an integrated circuit that substitutes for the LSIappears, it is also possible to use an integrated circuit to which thetechnology applies.

Moreover, each functional block or various features of the base stationdevice and the terminal device used in each of the aforementionedembodiments may be implemented or executed by a circuitry, which istypically an integrated circuit or a plurality of integrated circuits.The circuitry designed to execute the functions described in the presentspecification may comprise a general-purpose processor, a digital signalprocessor (DSP), an application specific or general applicationintegrated circuit (ASIC), a field programmable gate array (FPGA), orother programmable logic devices, discrete gates or transistor logic, ora discrete hardware component, or a combination thereof. Thegeneral-purpose processor may be a microprocessor, or alternatively, theprocessor may be a conventional processor, a controller, amicrocontroller, or a state machine. The general-purpose processor oreach circuit described herein may be configured by a digital circuit ormay be configured by an analogue circuit. Further, when a technology ofmaking into an integrated circuit superseding integrated circuits at thepresent time appears due to advancement of a semiconductor technology,the integrated circuit by this technology is also able to be used.

As used herein, the term “and/or” should be interpreted to mean one ormore items. For example, the phrase “A, B and/or C” should beinterpreted to mean any of: only A, only B, only C, A and B (but not C),B and C (but not A), A and C (but not B), or all of A, B, and C. As usedherein, the phrase “at least one of” should be interpreted to mean oneor more items. For example, the phrase “at least one of A, B and C” orthe phrase “at least one of A, B or C” should be interpreted to mean anyof: only A, only B, only C, A and B (but not C), B and C (but not A), Aand C (but not B), or all of A, B, and C. As used herein, the phrase“one or more of” should be interpreted to mean one or more items. Forexample, the phrase “one or more of A, B and C” or the phrase “one ormore of A, B or C” should be interpreted to mean any of: only A, only B,only C, A and B (but not C), B and C (but not A), A and C (but not B),or all of A, B, and C.

What is claimed is: 1-4. (canceled)
 5. A user equipment (UE) comprising:reception circuitry configured to receive downlink control information(DCI) on a physical downlink control channel (PDCCH); control circuitryconfigured to determine a transport block size (TBS) for a physicaluplink shared channel (PUSCH); and transmission circuitry configured totransmit the PUSCH based on the DCI, wherein in a case that a PUSCHmapping type B and more than one PUSCH repetition are applied, the DCIincludes information on a starting orthogonal frequency divisionmultiplexing (OFDM) symbol, a number of scheduled OFDM symbols of arepetition of the PUSCH, and a number of repetitions of the PUSCH; andthe TBS is determined based on a number of resource elements (REs) of ademodulation reference signal (DMRS) and the number of scheduled OFDMsymbols of the repetition.
 6. The UE according to claim 5, wherein in acase the repetition has multiple segments, the TBS for each of themultiple segments is determined based on the number of REs of the DMRSand the number of scheduled OFDM symbols of the repetition.
 7. A methodperformed by a user equipment (UE), the method comprising: receivingdownlink control information (DCI) on a physical downlink controlchannel (PDCCH); determining a transport block size (TBS) for a physicaluplink shared channel (PUSCH); and transmitting the PUSCH based on theDCI, wherein in a case that a PUSCH mapping type B and more than onePUSCH repetition are applied, the DCI includes information on a startingorthogonal frequency division multiplexing (OFDM) symbol, a number ofscheduled OFDM symbols of a repetition of the PUSCH, and a number ofrepetitions of the PUSCH; and the TBS is determined based on a number ofresource elements (REs) of a demodulation reference signal (DMRS) andthe number of scheduled OFDM symbols of the repetition.
 8. A basestation comprising: transmission circuitry configured to transmitdownlink control information (DCI) on a physical downlink controlchannel (PDCCH); control circuitry configured to determine a transportblock size (TBS) for a physical uplink shared channel (PUSCH); andreception circuitry configured to receive the PUSCH based on the DCI,wherein in a case that a PUSCH mapping type B and more than one PUSCHrepetition are applied, the DCI includes information on a startingorthogonal frequency division multiplexing (OFDM) symbol, a number ofscheduled OFDM symbols of a repetition of the PUSCH, and a number ofrepetitions of the PUSCH; and the TBS is determined based on a number ofresource elements (REs) of a demodulation reference signal (DMRS) andthe number of scheduled OFDM symbols of the repetition.
 9. The basestation according to claim 8, wherein in a case the repetition hasmultiple segments, the TBS for each of the multiple segments isdetermined based on the number of REs of the DMRS and the number ofscheduled OFDM symbols of the repetition.